Supply bbox on gpkg publish so GeoServer skips getBounds#78
Merged
Conversation
Even with 2D geometries, GeoServer still hit a 3D-CRS error computing the layer extent when publishing the featuretype: 500 ... java.io.IOException: Error occured calculating bounds for nm_tds_summary Compute the bbox from the GeoDataFrame and pass nativeBoundingBox + latLonBoundingBox (EPSG:4326) in the featuretype POST, with recalculate= empty so GeoServer keeps the supplied boxes instead of calling getBounds on the gpkg store. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
|
Your pull request is automatically being deployed to Dagster Cloud.
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Even after flattening to 2D, publishing the featuretype still failed:
GeoServer computes the layer extent by calling
getBounds()on the GeoPackage store, which still trips the 3D-CRS dimension bug at publish time — independent of geometry Z.Fix: compute the bbox from the GeoDataFrame and pass
nativeBoundingBox+latLonBoundingBox(EPSG:4326, also setnativeCRS) in the featuretype POST, withrecalculate=(empty) so GeoServer keeps the supplied boxes instead of recomputing._geojson_to_geopackagenow returns(gpkg_path, bbox).publish_geopackagetakesbboxand includes both bounding boxes.Verified: flake8 clean; conversion returns a correct 2D bbox from a 3D input feature.
🤖 Generated with Claude Code